Versions:
ShipRig is a release management tool published by RigSmith that unifies the changeset-to-version-to-publish workflow across every software ecosystem. Its core purpose is to give development teams a single, consistent process for recording changes, calculating version bumps, and publishing packages, regardless of the language, package manager, or registry involved. Instead of maintaining separate release tooling for each ecosystem in a polyglot codebase, teams can rely on ShipRig to apply the same uniform pipeline everywhere, reducing configuration drift and the risk of human error during releases. This makes it particularly well suited to monorepos and multi-language projects where components written in different ecosystems must be versioned and published in a coordinated, predictable manner. Typical use cases include automating semantic version calculation from structured changeset files, generating changelogs that accurately reflect each release, and pushing published artifacts to the appropriate registries for each ecosystem in a controlled order. Continuous integration pipelines can invoke ShipRig to turn merged changesets into published releases without manual intervention, while release managers can use it to preview pending version bumps before anything is published. Teams practicing trunk-based development or frequent small releases benefit from the enforced uniformity, since every package follows identical rules from intent to publication. Within a software catalog, ShipRig fits the developer tools category, specifically release automation, versioning, and package publishing. It sits alongside changelog generators, changeset managers, and CI-oriented deployment utilities, and complements build systems rather than replacing them. The current version of ShipRig is 1.18.0, reflecting an actively maintained product with a mature feature set. The catalog records 23 versions in total, indicating a substantial release history and ongoing iteration by RigSmith. Users evaluating the tool can consult the version history to track how the uniform release pipeline has evolved and to select the release line that matches their environment's requirements.
Tags: